Preview the changes: https://turinglang.org/docs/pr-previews/632
Please avoid using the search feature and navigation bar in PR previews!

https://turinglang.org/docs/pr-previews/632/uri/initial-parameters redirects to https://turinglang.org/docs/usage/troubleshooting/#initial-parameters

I see the intent here, although I can't help but get the feeling that it might be a bit overkill. Also specifying the redirect in a different page from the troubleshooting page means that if you do actually move the troubleshooting qmd file, you have to remember to edit the redirect page, which feels quite unlikely.

Would it be sufficient to add an aliases in the troubleshooting page itself? And maybe add a comment in the page itself to say that 'this URL is used in Turing.jl here, if you move this file please make sure to retain it'?

Would it be sufficient to add an aliases in the troubleshooting page itself?

In the long run, we may need more redirects, so having them in one place helps with scalability and maintenance. Adding aliases in the individual page works too, but isn’t ideal if there are many redirects. Also, if a page gets moved, it's likely by one of us who knows the workflow. I suggest we just add a note in the README to make that clear.

Also, if a page gets moved, it's likely by one of us who knows the workflow.

Probably yes, but even though I've seen this PR, I guarantee I'll forget.

I think the best solution is a link checker in CI (not for this PR, maybe one day).

I think the best solution is a link checker in CI (not for this PR, maybe one day).

I remember we also have a issue for this, will try to fix it someday!

Would it be sufficient to add an aliases in the troubleshooting page itself? And maybe add a comment in the page itself to say that 'this URL is used in Turing.jl here, if you move this file please make sure to retain it'?

I like @penelopeysm's proposal here. The current approach seems overkill -- it's unlikely we will have lots of redirects.

I agree to both of you but using aliases in file itself will redirect to https://turinglang.org/docs/usage/troubleshooting/ page and not some particular section link like https://turinglang.org/docs/usage/troubleshooting/#initial-parameters -- We can only achieve it using current approach.

@AoifeHughes Please feel free to use this based on your requirements in this PR -- TuringLang/Turing.jl#2637 (comment)